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

Sequence contains no matching element when reading OCL with a step package #7648

Closed
1 task done
YuKitsune opened this issue Jul 4, 2022 · 2 comments
Closed
1 task done
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving p2 state/happening Currently in progress (4/4)

Comments

@YuKitsune
Copy link
Contributor

Team

  • I've assigned a team label to this issue

Severity

Blocking a small number of customers.

Version

Earliest tried was 2022.3.4128

Latest Version

I could reproduce the problem in the latest build

What happened?

When storing an aws-ecs step in OCL, and specifying environment variables for the container, Octopus will throw the following error when attempting to load the deployment process:

System.InvalidOperationException: Sequence contains no matching element

Reproduction

  1. Create a git project
  2. Create a step using the aws-ecs step package
  3. Specify environment variables for the container
  4. Commit the deployment process
  5. Attempt to get the deployment process via Octopus
  6. 💥

Example OCL:

step "Deploy Service ECS" {
    action {
        action_type = "aws-ecs"
        step_package_version = "1.3.0"

        inputs {
            containers {
                containerName = "foobar"

                environmentVariables {
                    key = "MY_ENV_VAR"
                    type = "plain"
                    value = "my value"
                }
            }
        }
    }
}

Error and Stacktrace

No response

More Information

No response

Workaround

No response

@YuKitsune YuKitsune added kind/bug This issue represents a verified problem we are committed to solving p2 state/happening Currently in progress (4/4) team/config-as-code labels Jul 4, 2022
@octoreleasebot
Copy link

Release Note: Fixed an issue where step packages stored in OCL were incorrectly deserialised.

@Octobob
Copy link
Member

Octobob commented Aug 29, 2022

🎉 The fix for this issue has been released in:

Release stream Release
2022.3 2022.3.4289
2022.4+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving p2 state/happening Currently in progress (4/4)
Projects
None yet
Development

No branches or pull requests

3 participants