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

Adding windows stack support #182

Closed
dbathgate opened this issue Mar 15, 2024 · 0 comments · Fixed by #184
Closed

Adding windows stack support #182

dbathgate opened this issue Mar 15, 2024 · 0 comments · Fixed by #184

Comments

@dbathgate
Copy link
Contributor

Overview

Cloud Foundry has support for running Windows workloads. There is the ability to have buildpacks that support both the cflinuxfs* and windows, but the compatibility for both needs to be maintained by the buildpack owner.

Proposed Solution

  • Buildpacks that support Windows need to have an equivalent Windows Batch script for compile and supply (supply.bat, compile.bat)
  • The 0001_retrieve-secrets.sh for exporting secrets as environment variables would need to be ported to a Windows Batch script as well
  • The Go executable would also need to be compile for the Windows OS

Additional Considerations

  • The Windows supported buildpack could either be in this repository and an entirely new repository
  • Developers could use Conjur SDK's to retrieve secrets programmatically rather than relying on the buildpack. The Windows buildpack primarily serves .NET Framework users so there would need to be a .NET framework SDK.

Proof-of-Concept

  • I have created a POC demonstrating how this buildpack would work on a Windows stack: Commit here
  • This POC is functional, but still needs some enhancements.
  • We may have a need for this in the future and I am looking to assess the possibility of this becoming a supported feature of this buildpack.
@szh szh linked a pull request May 22, 2024 that will close this issue
13 tasks
@szh szh closed this as completed in #184 May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant