Replies: 1 comment 1 reply
-
|
Hey @morgoth! If I understo 8000 od correctly, you can set up a different profile just by editing the command that generates the temporary password # my config/deploy.yml
<% ENV["AWS_PROFILE"] = "kamal-servers" unless ENV["CI"] %>
registry:
server: xxx.amazonaws.com
username: AWS
password: <%= %x(aws ecr get-login-password --profile YOUR_PROFILE) %> # change this line |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@eduardoyutaka That's exactly how I'm doing this in the example above. BTW when setting ENV["AWS_PROFILE"] there is no need to pass it to the command as it's picked by the cli by default. I'm just wondering if such setup could be done in cleaner way via hook |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to ask for a feedback if the hook that is run before executing any of the kamal command would be useful to more people?
My usecase is to set up AWS config, so the AWS services are reachable. Currently I'm doing it like this:
Here, locally I'm having few AWS profiles, and based on the app/destination I want to choose the proper one.
On the CI, where the CD is implemented I don't need any profiles switching.
With the pre-command hook this could be done transaprently to the final
config/deploy.ymlWhat do you think?
Beta Was this translation helpful? Give feedback.
All reactions