[CT-2756] [Bug] relation_name is always None on SeedNode

[aranke]

Found during 🎩 for #7881

A/C:

1. relation_name is correct on SeedNode

[jtcohen6]

@aranke Is relation_name always none? Or at a specific point in time where we expect it to be populated?

This is running off the main branch (v1.6.0-b8):

$ dbt -q ls --resource-type seed --output json --output-keys name relation_name
{"name": "my_seed", "relation_name": "\"jerco\".\"dbt_jcohen\".\"my_seed\""}

Looking at e761aa0: Is it possible that this issue is about compiled_code, rather than relation_name? It's true that a seed's raw_code and compiled_code are both always None!

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[dbeatty10]

Re-opened since we have some source code pointing to this issue:

dbt-core/core/dbt/context/providers.py

Lines 1468 to 1470 in 2411f93

	if getattr(self.model, "defer_relation", None) and self.config.args.which == "clone":
	# TODO https://github.com/dbt-labs/dbt-core/issues/7976
	return f"select * from {self.model.defer_relation.relation_name or str(self.defer_relation)}" # type: ignore[union-attr]

If we want to re-close this for some reason, then we should consider removing that comment in the source code as well.