Change Details

As an initial implementation, instead of immediately creating a new Salt execution module, **I will temporarily use cmd.run to configure CARP.** This approach allows us to: 1. Retrieve easily the CARP shared secrets from Vault. 2. Generate easily the necessary CARP configuration (rc.conf entries). This is intended as a short-term solution to validate the configuration and integration with Vault. **A future refactoring may introduce a dedicated ra carp execution module for better maintainability and abstraction.** Steps: [x] Create the role folder "router" [x] Create the required init.sls file [] Create the new state carp inside a folder carp created [] Deploy the network configuration to router-002 and router-003 via Salt, and validate CARP is correctly applied. And then : We can return to to T2203, and finish the step "Deploy the updated file nodes.sls and apply the configuration via Salt on every machine"

As an initial implementation, instead of immediately creating a new Salt execution module, **I will temporarily use cmd.run to configure CARP.** This approach allows us to configure easily the CARP configuration (rc.conf entries). This is intended as a short-term solution to validate the configuration and integration with Vault. **A future refactoring may introduce a dedicated a carp execution module for better maintainability and abstraction.** Steps: [x] Create the role folder "router" [x] Create the required init.sls file [] Create the new state carp inside a folder carp created [] Deploy the network configuration to router-002 and router-003 via Salt, and validate CARP is correctly applied. And then : We can return to to T2203, and finish the step "Deploy the updated file nodes.sls and apply the configuration via Salt on every machine"

As an initial implementation, instead of immediately creating a new Salt execution module, **I will temporarily use cmd.run to configure CARP.** This approach allows us to: 1. Retrieve easily the CARP shared secrets from Vault. 2. Generatto configure easily the necessarye CARP configuration (rc.conf entries). This is intended as a short-term solution to validate the configuration and integration with Vault. **A future refactoring may introduce a dedicated ra carp execution module for better maintainability and abstraction.** Steps: [x] Create the role folder "router" [x] Create the required init.sls file [] Create the new state carp inside a folder carp created [] Deploy the network configuration to router-002 and router-003 via Salt, and validate CARP is correctly applied. And then : We can return to to T2203, and finish the step "Deploy the updated file nodes.sls and apply the configuration via Salt on every machine"