move dagster-cloud to setup.py, remove requirements.txt

[yuhan]

having both is confusing. this pr moves dagster-cloud (should it be dagster-cloud or dagster_cloud??) to setup.py and gets rid of requirements.txt. note that this means in local dev, the user would install dagster-cloud (which is probably fine and maybe preferred because it includes the deploy CLI)

Test plan

~/dev/dagster-cloud-serverless-quickstart main*
demo-1006 $ dagster-cloud configure
demo-1006 $ dagster-cloud serverless deploy \
  --location-name status-quo-quickstart \
  --package-name myd_agster_project

deployed the code location successfully -- i believe we don't need to deal with backcompat because the dockerfile does pip install conditionally based on the existence of requirements.txt and setup.py

[yuhan]

Current dependencies on/for this PR:

• main
  • PR move dagster-cloud to setup.py, remove requirements.txt #21 👈

This comment was auto-generated by Graphite.

[github-actions]

Your pull request is automatically being deployed to Dagster Cloud.

Location	Status	Link	Updated
example_location		Deploy failed	Oct 07, 2022 at 06:44 AM (UTC)

[shalabhc]

This will work for the new serverless stuff we are working on. I'm not sure if there are hard dependencies on the requirements.txt being present with the existing serverless workflows. Are you able to test it? I think this will go live as soon as it is merged, right?

[yuhan]

i think it works with the existing docker build because of this check

i tested from my local (against master i think) and used the CLI to deploy this template to my cloud org.

and yea.. it will go live as long as it's merged which is not good - some relevant convo about better test set up for this template

[shalabhc]

I think we should switch to using dashes in the python package names so it matches pypi? eg https://pypi.org/project/dagster-cloud/ and https://pypi.org/project/dagster-aws/

[yuhan]

i forgot to land this. sorry about that!