Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Is There A Way To Specify The Project And Name Of A Pipeline Defined With Decorators At Runtime? I Tried To Change The Properties Of The Current Task, The Name Is Updated Correctly But When I Try To Move The Task To Another Project It Disappears From The

Is there a way to specify the project and name of a pipeline defined with decorators at runtime? I tried to change the properties of the current task, the name is updated correctly but when I try to move the task to another project it disappears from the PIPELINES tab in the UI.

@PipelineDecorator.pipeline(name='Fixed name', project='Fixed project')
def run_pipeline(config):
    pipeline_task = Task.current_task()
    pipeline_task.move_to_project(new_project_name=f'{config.project_id}/.pipelines')
    pipeline_task.set_name(config.run_name)
  
  
Posted one year ago
Votes Newest

Answers 5


What happens if you set the new project name to f"{config.project_id}" (notice, no .pipelines )?

  
  
Posted one year ago

Hi @<1570220858075516928:profile|SlipperySheep79> , I see no reason you shouldn't be able to. Are these the only actions you're doing? Does it happen to you with only decorators or also pipelines from tasks & functions?

  
  
Posted one year ago

I think I found a solution using pipeline_task.move_to_project(new_project_name=f'{config.project_id}/.pipelines/{config.run_name}', system_tags =['hidden', 'pipeline'])

  
  
Posted one year ago

Same thing, it's not visible under PIPELINES

  
  
Posted one year ago

Yes these are the only actions. The task is moved correctly tho, I can see it under f'{config.project_id}/.pipelines' in the UI, the issue is that it's not visible under PIPELINES . I haven't tried with tasks or fiunctions pipelines yet.

  
  
Posted one year ago
949 Views
5 Answers
one year ago
one year ago
Tags
Similar posts