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

Move remaining Operate, Test, and Deploy content #27087

Merged
merged 39 commits into from
Jan 15, 2025

Conversation

neverett
Copy link
Contributor

Summary & Motivation

Move content into Operate, Test, and Deploy sections of new docs.

How I Tested These Changes

Local build.

Changelog

Insert changelog entry or delete this section.

@neverett neverett added the area:docs-revamp Related to the revamp of the docs label Jan 14, 2025
@neverett neverett self-assigned this Jan 14, 2025
@neverett neverett marked this pull request as ready for review January 15, 2025 07:52
Copy link

github-actions bot commented Jan 15, 2025

Deploy preview for dagster-docs-beta ready!

Preview available at https://dagster-docs-beta-mctubl8tl-elementl.vercel.app

Direct link to changed pages:

@neverett neverett requested review from cmpadden and dehume January 15, 2025 08:28
Copy link
Contributor

@dehume dehume left a comment

Choose a reason for hiding this comment

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

Overall looks good. Found a couple of nits. And 2 larger questions:

  • For some of the older guides like k8s the language is around ops. Is there a ticket to eventually rework them to be assets? And when talking about the node abstraction in general, does ops include both ops and assets?
  • Noticed their is some inconsistency when referring to the OSS platform. Sometimes it is "Dagster Open Source" or"Dagster Open Source (OSS)" or just "Open Source". Didn't know what the preferred standard is.

)
```

It is recommenced to include definitions in a Python module named `definitions.py`.
Copy link
Contributor

Choose a reason for hiding this comment

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

@cmpadden if this is true, should Dagster U get updated and have the Definitions moved out of the __init__.py

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, that is a more recent (last year) best practice, and I think DU should be updated.

{/* TODO turn back into <CodeReferenceLink> once that's implemented */}
:::tip

You can find the code for this example on [GitHub](https://github.com/dagster-io/dagster/tree/1.9.8/examples/deploy_ecs).
Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason this Github link is pinned to 1.9.8?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In old docs, this link is generated by a <CodeReferenceLink> component, but that component isn't implemented in new docs. This is basically a placeholder link until we implement that component -- here's the relevant Linear ticket: https://linear.app/dagster-labs/issue/DOC-685/implement-codereferencelink-component

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This should probably just be https://github.com/dagster-io/dagster/tree/master/examples/deploy_ecs in the meantime, though; I can change that.


In this case, you'll want to ensure you provide the right connection strings for your Cloud SQL instance, and that the node or container hosting the webserver is able to connect to Cloud SQL.

Be sure that this file is present, and _DAGSTER_HOME_ is set, on the node where the webserver is running.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Be sure that this file is present, and _DAGSTER_HOME_ is set, on the node where the webserver is running.
Be sure that this file is present, and `_DAGSTER_HOME_` is set, on the node where the webserver is running.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 2c1ce41


Refer to the [boto3 docs](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ecs.html#ECS.Client.run_task) for the full set of available arguments to `run_task`. Additionally, note that:

- Keys are in `camelCase` as they correspond to arguments in boto's API
Copy link
Contributor

Choose a reason for hiding this comment

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

Does camelCase need to be formatted as code?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, I'll remove that formatting.


## Pipes protocol

The Pipes protocol is used to integrate with systems that have their own execution environments. It enables running code in these external environments while allowing Dagster to maintain control and visibility. Example implementations of this approach include [AWS Lambda](https://github.com/dagster-io/dagster/tree/d4b4d5beabf6475c7279b7f02f893a506bca0bb0/python_modules/libraries/dagster-aws/dagster_aws/pipes), [Databricks](https://github.com/dagster-io/dagster/blob/d4b4d5beabf6475c7279b7f02f893a506bca0bb0/python_modules/libraries/dagster-databricks/dagster_databricks/pipes.py), and [Kubernetes](https://github.com/dagster-io/dagster/blob/d4b4d5beabf6475c7279b7f02f893a506bca0bb0/python_modules/libraries/dagster-k8s/dagster_k8s/pipes.py).
Copy link
Contributor

Choose a reason for hiding this comment

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

All the links are tied to a specific branch

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good catch

@neverett neverett merged commit ebade5e into master Jan 15, 2025
2 of 3 checks passed
@neverett neverett deleted the nikki/docs/move-more-guides-content branch January 15, 2025 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:docs-revamp Related to the revamp of the docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants