Releases: F5Networks/f5-bigip-runtime-init
Releases · F5Networks/f5-bigip-runtime-init
1.4.4
Issues Resolved:
- Updated base schema to allow resolution of Azure secrets that reference other runtime parameters
1.4.3
Documentation:
- README and examples updates
1.4.2
Bugs fixed:
- Fixed GitHub Issue #40 by adding a Google URL example.
- Fixed GitHub Issue #35 by suppressing logs if a command-based attribute contains a Type SECRET parameter.
Documentation:
- Overall enhanced code examples. Additionally, examples that can be copy/pasted are now labeled separately from code examples meant for READMEs.
- Added logging control blocks to all examples so users can easily toggle to debug.
1.4.1
Features added:
- Added a new AWS instance metadata provider runtime parameter URI type for retrieving values from instance metadata without needing to explicitly retrieve a session token.
- Added a new tag type runtime parameter for discovering cloud provider tag values from the BIG-IP instance.
- The URL type runtime parameter now supports local file URLs.
Issues Resolved:
- Added a check to verify the configuration file is valid JSON or YAML. F5 BIG-IP Runtime Init returns a helpful error message in the case of a malformed declaration. Fixes GitHub Issue #33.
1.4.0
Features added:
- AWS IMDSv2 Support
- Metadata Provider defaults to IMDSv2 first
- Ability to reference runtime variable in another runtime variable (ex. to pass tokens)
- Hashicorp Vault Support
Issues Resolved:
- Update AWS Cloud provider to resolve Gateway correctly for subnet-ipv4-cidr-block. (#28)
1.3.2
Bugs fixed:
- Updated logging to hide sensitive data
- Fixed issue when verifyTls setting can't be set to false value
1.3.1
Features added:
- Enabled verifyTls setting for runtime_parameters field
Bugs fixed:
- Addressed issue with hard-coded field in Hashicorp Vault Client
- Fixed the problem when sensitive values are not hidden in logs
- Removed Hashicorp Vault namespace from schema. The namespace needs to be passed as part of secretPath value. Link to Hashicorp Vault docs for more details: https://www.vaultproject.io/api#namespaces
1.3.0
Features added:
- Added support for Hashicorp Vault to use as a cloud-independent secret vault for users with a multi-cloud deployment.
- Added controls parameter for logging level.
- Added support for running ipcalc on additional inputs.
- Runtime-Init will now always have the latest tool chain packages when users download the file from CDN.
Bugs fixed:
- Additional validation on runtime params return values.
Documentation:
- Added a note to the README that Runtime-Init currently does not handle declarations that require reboot.
- Added troubleshooting information about the Extension metadata file to the README.
1.2.1
Features Added:
- Added ability to use metadata substitutions in bigip_ready_enabled and post_onboard_enabled command hooks.
- Added additional logging for configuration loading errors.
- Added network formatting convince function.
- Resolved noted dependency vulnerabilities.
- Added check for failed 404 error when posting declarations and retry.
- Enhance install_rpm script to mitigate failures due to unstable network.
- Added FAST support for extension packages.
- Added ability to use MAC address to locate Azure IP addresses.
- Teem data now includes anonymous template data.
- Updates to Automation Toolchain metadata to support latest versions of DO, AS3, CFE, FAST, and TS.
Bugs Fixed:
- Fixed an issue that caused Declarative Onboarding (DO) failure by preventing Runtime-Init from discovering MAC addresses.
1.2.0
Features added:
- Users can now provide the URL of the tool chain API without specifying the version.
Bugs fixed:
- Fixed an issue that made runtime secrets visible in log messages.
- Fixed an issue that caused runtime to report "All operations finished successfully" when declarations are not successful.
- Fixed GitHub issue #10.