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

Ideas for next releases #36

Open
infra-monkey opened this issue Aug 2, 2024 · 4 comments · Fixed by #41
Open

Ideas for next releases #36

infra-monkey opened this issue Aug 2, 2024 · 4 comments · Fixed by #41
Labels
enhancement New feature or request

Comments

@infra-monkey
Copy link
Contributor

Description

Here is a list of developments that could be good to implement. And before you ask I am willing to work on them :)

  • Migrate to the Terraform Plugin Framework. Not critical but easier to do now than when the provider will get bigger.
  • Move the go-freeipa dependency to upstream instead of your fork. I have not seen blocking issues using the upstream. Of course upstream will need to update the generated code and errors as it is based on freeipa-4.6 api.
  • Implement datasources where it makes sense
  • Implement import of resource in order to allow easy management of existing freeipa clusters with terraform.
  • Add relevant resource type, like vault, external idp, idviews
  • Fix some naming choices in resource names or

Open questions

Any issue I might have missed in the different points? go-freeipa dependency and plugin framework might be the trickiest as it depends on historical changes I might not be aware of.

Any thoughts on priority?

Which would be the best resource types to implement?

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@infra-monkey infra-monkey added the enhancement New feature or request label Aug 2, 2024
@jagular-spb
Copy link

  • to datasources

@philip-harvey
Copy link

Hello!
We use a few ipa servers, like ipa_server = srv, server-1.com, server-2.com. They are replicas, and it works nicely if I configure them via Ansible.

However, in the module, I can only use one freeipa_host in provider as I see in examples...
Could you please add support for multiple ipa hosts?

@infra-monkey
Copy link
Contributor Author

Hello @philip-harvey
Can you please open a separate issue for your question.
also provide more details of what you are trying to do and resource examples.
thank you

@philip-harvey
Copy link

Hello @philip-harvey Can you please open a separate issue for your question. also provide more details of what you are trying to do and resource examples. thank you
Sure thing.

#42

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

Successfully merging a pull request may close this issue.

4 participants