-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/ignition: migration from resources to data resources #11851
Conversation
Hi @mcuadros Thanks for the work here - I understand why we need to do this. Right now, this is backwards incompatible - which means we would need to duplicate the resources and deprecate the old ones etc Luckily, the awesome @apparentlymart, wrote a shim function that he has used to map resources to data_sources You can see an example of it here This would then allow us to keep backwards compatibility with older versions :) Thoughts? Paul |
@stack72 done |
@stack72 ping |
@@ -19,6 +19,19 @@ Use the navigation to the left to read about the available resources. | |||
This config will write a single service unit (shown below) with the contents of an example service. This unit will be enabled as a dependency of multi-user.target and therefore start on boot | |||
|
|||
``` | |||
<<<<<<< HEAD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a merge that failed?
systemd = [ | ||
"${data.ignition_systemd_unit.example.id}", | ||
] | ||
======= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merge conflict?
@mildred nice catch! solved |
Pulled down this branch and started working with it. Any idea on amount of time left to review? |
By the way, we are using this in production and it works well. |
👍 I would also like to see this merged. It's a biting us a little bit, using the latest stable release. |
LGTM! Thanks for the work here - sorry it took so long
|
* provider/ignition: migration from resources to data resources * website: provider/ignition documention updated to data resources * provider/ignition: backwards compatibility support for old resources
…orp#11851) * provider/ignition: migration from resources to data resources * website: provider/ignition documention updated to data resources * provider/ignition: backwards compatibility support for old resources
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Fixes: #11518