[Scaling]

[himani2411]

Description of changes

• Describe what you're changing and why you're doing these changes.

Tests

• Describe the automated and/or manual tests executed to validate the patch.
• Describe the added/modified tests.

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[gmarciani]

It looks like this Pr can be closed as we already merged the fixed to cfninit in a different PR.