Code Monkey home page Code Monkey logo

Comments (5)

ksharma-qc avatar ksharma-qc commented on September 27, 2024 1

thanks for outlining these details. I guess one workaround for now is to use a non-dictionary variable for those variables you want set by the survey form

@mabashian do you know if the expectation is the survey value to be injected into a dictionary? is this fixed in the new UI?

New UI? I'm currently at the latest version of AWX.

The problem with workaround is that'll require me to modify the code for playbooks which haven't been written by me.

The expectation is for the values to be injected into the dictionary yes. inputs.a.b should translate to:

inputs:
  a:
     b:

Furthermore, the dictionary should be merged into any existing ones if ANSIBLE_HASH_BEHAVIOUR is set to merge.

from awx.

jacobemery avatar jacobemery commented on September 27, 2024 1

Also found this to be true. The default values appear in the survey summary and can be curl'd, but they don't pre-populate in the survey.

The workaround provided by @fosterseth isn't suitable for me either, as the playbook was written by someone else. I could go through the process of opening a PR and changing all their variables to strings... but with a lot of variables, that's kinda rough and the author may not like that.

I know there's a new UI coming soon, is this is being worked on? I took a peak at the tech preview, but the survey screen is unavailable at the moment, so it's hard to tell.

Thanks!

from awx.

fosterseth avatar fosterseth commented on September 27, 2024

thanks for outlining these details. I guess one workaround for now is to use a non-dictionary variable for those variables you want set by the survey form

@mabashian do you know if the expectation is the survey value to be injected into a dictionary? is this fixed in the new UI?

from awx.

fosterseth avatar fosterseth commented on September 27, 2024

@ksharma-qc thanks, yes sounds like a bug that would need some UI work to address

from awx.

jon-nfc avatar jon-nfc commented on September 27, 2024

Just discovered this issue and without even knowing it, I have this problem and didn't realize it was due the variable to set being a dict key. in my case module_database.name

I thought there was a bug in the UI for having require: true, so un-checked it for the survey question and now the survey gives no errors and the job template runs as it should. I just can't make the question mandatory.

from awx.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.