Skip to content
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

Feature request- MCA Invoice Section Module #2015

Open
1 task done
arne21a opened this issue Jun 19, 2024 · 0 comments
Open
1 task done

Feature request- MCA Invoice Section Module #2015

arne21a opened this issue Jun 19, 2024 · 0 comments

Comments

@arne21a
Copy link
Contributor

arne21a commented Jun 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

As part of our subscription vending process, we are creating an invoice section per landing zone.
There is currently no way to automate this using aztfmod. These is also currently no terraform resource, we can use azapi though.
The created invoice section should also be available for reference when creating subscriptions
I will provide a proposal for this module.

New or Affected Resource(s

azapi_resource, invoice_section

Potential Configuration file

invoice_sections = {
  section_1 = {
    name = "my-sandbox-invoice-section"
    billing_account_id = "0000-000-000:000-0000-000_2019-05-31"
    billing_profile_id = "XXXX-XXXX-XX-XXXX"
    labels = {
      "foo" = "baz"
    }
    tags = {
      "tagA" = "valueA"
    }
  }
}

References

No response

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

No branches or pull requests

1 participant