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

Using compute target name as a PipelineParameter #1934

Open
roshan-chistats opened this issue Aug 16, 2023 · 0 comments
Open

Using compute target name as a PipelineParameter #1934

roshan-chistats opened this issue Aug 16, 2023 · 0 comments

Comments

@roshan-chistats
Copy link

I have a query regarding the behavior of the azureml.pipeline.core.graph.PipelineParameter class. As its name suggests, the PipelineParameter is employed to dynamically pass values to our pipeline after its publication. My objective is to convey dynamic values to the orchestrating notebook. For instance, I intend to provide the compute target name dynamically once the pipeline is published. What I am implying is that users can specify the compute name afterwards, eliminating the need for hardcoding the same.

The code i tried:

ws = Workspace.from_config()
compute_para = PipelineParameter(name="compute_parameter", default_value="vm1-ig-04-aml-in-cappa-d")
compute_target = ComputeTarget(workspace=ws, name=compute_para.default_value)

As I have assigned the default value of the compute name to the compute target, it is currently utilizing only the default value. My inquiry pertains to the existence of any available functionality within Azure that allows for the dynamic transmission of values to the orchestrating notebook.

Let me know if you need more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant