Enable copilot env init command to configure ALB access logs

[okram999]

Ability to configure ALB access logs is only confined to defining the configuration in the environment's manifest file as specified here. Enabling the same feature in the copilot's CLI as an argument will also make things simple for customers that are scripting using co-pilot.

Something like this: copilot env init -n some_name --profile default --container-insights --http public --access_logs true

[Lou1415926]

Hello @okram999 ! Is some_name always the same across the executions of the script? If you have an environment manifest at copilot/environments/test/manifest.yml in the workspace, copilot env init --name test will reuse that manifest. Does this work for your use case?

[okram999]

@Lou1415926 - Not in this case, although i understand what you are suggesting. Use case here is, i already have a project with the application and i want to spin up a whole new environment to deploy the service. The flow is like:

copilot env init --> env deploy --> svc deploy --name <svc_name> --env <env_name_deployed_earlier>

[Lou1415926]

@okram999 Gotcha. Just a clarification question - do you push your entire copilot/ folder, which includes the .workspace file and the service manifests, into the runtime where the script execution happens?

[efekarakus]

(seems to be also related to "preview environments" https://github.com/aws/copilot-cli/issues/1159)

[github-actions[bot]]

This issue is stale because it has been open 60 days with no response activity, and is tagged with pending/question. Remove the stale label, add a comment, or this will be closed in 14 days.