enable coreos support for IBM Cloud Satellite location creation

[bhpratt]

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 other comments that do not add relevant new information or questions, 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

IBM Cloud Satellite now support coreos host OS for control plane and worker nodes. Requires a new location.

New or Affected Resource(s)

TBD. I think this only affects satellite location create.

• ibm_XXXXX

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

• support has been added to the go-sdk: added coreosenabled option to create location and test container-services-go-sdk#4 (comment)

[bhpratt]

Looks like I can't assign users - but I'd like to take this issue.

[bhpratt]

need this PR merged in containers sdk: https://github.com/IBM-Cloud/container-services-go-sdk/pull/5/files

[darrellschrag]

Also need to make sure you can get the attach CoreOS ignition script from the location once this capability has been added.

[andrewferrier]

As @darrellschrag says, I think this affects ibm_satellite_location resource and ibm_satellite_attach_host_script data source.

[andrewferrier]

Looks like the change for ibm_satellite_location has gone in, but the one for ibm_satellite_attach_host_script is still pending?

[andrewferrier]

@hkantare which version of the provider contains this change to the host attach script?

[hkantare]

We are planning for a beta release mostly by tomrrow EOD