Skip to content

Add support for billing tags #398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 12, 2018
Merged

Conversation

tduffield
Copy link
Contributor

Adds two new configuration values (BuildkiteBillingTagName and BuildkiteBillingTagValue) that can be used to apply a Cost Allocation Tag to instances created by the ASG.

Adds two new configuration values (`BuildkiteBillingTagName` and
`BuildkiteBillingTagValue`) that can be used to apply Cost Allocation
Tag to instances created by the ASG.

Signed-off-by: Tom Duffield <tom@chef.io>
@lox
Copy link
Contributor

lox commented Apr 3, 2018

I wonder if these need to be configurable, vs just adding the aws:createdBy with something to indicate elastic stack.

Ideally we'd like to keep parameters to a minimum, as they make it harder for people to understand what needs configuring.

If you wanted arbitrary tags, presumably you could just use the Additional Tags section when you are creating the cloudformation stack?

@tduffield
Copy link
Contributor Author

tduffield commented Apr 3, 2018

They need to be configurable because people may use a different tag other than aws:createdBy to manage cost centers. For example, my team uses X-Application.

As for the Additional Tags section, those are buildkite tags and we need very specific AWS tags to use in Cost Center.

Having the default be aws:createdBy should mean that most people won't need to overwrite the default. But for those who care, they can. To me that feels like a valuable parameter. Especially when it puts me in a position where I can track exactly how much $$ I'm saving using Buildkite (which is the legitimate reason why I want the tag)

@tduffield
Copy link
Contributor Author

@lox have you had an opportunity to think on this any more?

@lox
Copy link
Contributor

lox commented Apr 12, 2018

Yup, let's merge it in. Thanks for this and thanks for your patience, have been at AWS Summit.

@lox lox merged commit f69c633 into buildkite:master Apr 12, 2018
@lox
Copy link
Contributor

lox commented Apr 15, 2018

Hmmmm. The build is failing with Your account is not allowed to create tag aws:createdBy

@lox
Copy link
Contributor

lox commented Apr 15, 2018

@tduffield I must admit, I still don't really understand why you need this if you use X-Application. You should just be able to specify that as an additional tag when creating the the Stack? For aws:* tags, I that doesn't seem to work, but should work fine for X-Application.

@tduffield
Copy link
Contributor Author

@lox where do I specify additional AWS tags?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants