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

Metaflow Configs #1962

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Metaflow Configs #1962

wants to merge 15 commits into from

Conversation

romain-intel
Copy link
Contributor

This is not yet fully ready but putting out so people can get a general sense of the direction.

@bhogan-bdai
Copy link

bhogan-bdai commented Aug 23, 2024

As a user interested in using a config file instead of using different sets of parameters, what would a config file look like?

@romain-intel
Copy link
Contributor Author

@bhogan-bdai -- the idea so far is to support a simple format like JSON (nested dicts basically) but other formats could be supported as well. We are also providing a parser option which means you would be able to write your own parser and would need to return a dict. If you have other ideas/wish-list type of things, please let us know though. This is still a WIP although it kind of works. I'll post an example script a bit later to show the functionality.

@romain-intel romain-intel changed the title [WIP] Initial Config object Metaflow Configs Sep 10, 2024
@romain-intel romain-intel marked this pull request as ready for review September 10, 2024 16:04
Previously, options like `branch` and `name` (injected by the project
decorator for example) could be set using `METAFLOW_BRANCH`. They now
need to be set using `METAFLOW_FLOW_BRANCH`.

This change is made to prevent clashes between regular metaflow
configuration settings and decorator level options.

No other changes are made so `METAFLOW_RUN_MAX_WORKERS` still works
as expected and `METAFLOW_PYLINT` as well.
Several fixes:
  - fixed an issue with default values
  - better handling of parameter defaults as configs
  - handle config defaults as functions
  - ConfigValue is more "dict"-like
  - made <myflow>.configs and <myflow>.steps work properly
  - renamed resolve_configs to init
Specifically:
  - moved things out of the INFO file
  - added to_dict
  - renamed user_configs to config_parameters
Specifically:
  - made config values immutable
  - cleaned up state stored in FlowSpec
  - added a test exercising configs in various places
@@ -135,8 +135,8 @@ class KubernetesDecorator(StepDecorator):
package_sha = None
run_time_limit = None

def __init__(self, attributes=None, statically_defined=False):
super(KubernetesDecorator, self).__init__(attributes, statically_defined)
def init(self):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something with this recent setup is causing kubernetes execution to fail:

in step_init
    if self.attributes["gpu_vendor"].lower() not in ("amd", "nvidia"):
AttributeError: 'NoneType' object has no attribute 'lower'

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

Successfully merging this pull request may close these issues.

3 participants