You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it make sense to include the fog credentials into the .opsicle file?
I have several apps, with different aws accounts, and it would be nice to have my opsicle config all in one place (and self contained in my project directory)
The text was updated successfully, but these errors were encountered:
That's an interesting thought; if it were implemented, I'd like to see it as an override in .opsicle so you can change it on a per app basis only if necessary.
I think it could make sense. But I don't want to require it that way, I'd like to be able to fall back on a shared config for a user. We have half a dozen apps that all use the same aws account so a shared file works well for us.
I do feel like the aws credentials bit is a bit awkward to be honest and I think there is room for improvement. We used the .fog file since it was a pattern we were already using.
My other concern is that we typically don't want to commit our aws credentials to a repository and putting somewhere outside of the app ensures that doesn't happen.
I'm still on the fence on whether this is a good idea or not. I feel like if we do it the opsicle config should be moved out of the app repository. I don't want to run the risk of users checking in their aws keys.
Would it make sense to include the fog credentials into the .opsicle file?
I have several apps, with different aws accounts, and it would be nice to have my opsicle config all in one place (and self contained in my project directory)
The text was updated successfully, but these errors were encountered: