Problem/Motivation

While sprinting, maxocub and I talked about the class property on the migration yml and that there wasn't any documentation for it. Not knowing where sure documentation should be, we asked phenaproxima where it should be documented and he wasn't sure either.

Proposed resolution

Add a handbook page to in this section, Upgrade using the user interface

Remaining tasks

Do it.

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

quietone created an issue. See original summary.

quietone’s picture

Add parent issue.

heddn’s picture

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

j. ayen green’s picture

Assigned: Unassigned » j. ayen green
j. ayen green’s picture

quiteone can you point me at an example of this, so I can try to narrow down the provenance of the code I need?

quietone’s picture

@j. ayen green, thanks for picking this up.

It is has been a long time since I spoke with maxocub about this but I think the idea was to build up documentation for all the migration properties. Some of course will be from the plugin system itself and, in my opinion, still worth documenting from a migration perspective. Then there are migration specific ones, like 'audit' and 'migration_tags' that could eventually be included. But one step at at time.

Migration plugins using the class property are:

  • d7_comment.yml
  • d7_field_instance_widget_settings.yml
  • d6_field_formatter_settings.yml
  • d7_field_instance.yml
  • d7_field.yml
  • d7_field_formatter_settings.yml
  • d6_field_instance.yml
  • d6_field_instance_widget_settings.yml
  • d6_field.yml
  • d6_node_translation.yml
  • d7_node_translation.yml
  • d6_profile_values.yml
  • d7_user.yml

Is that what you are looking for?

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Active » Fixed

I been scanning and reading the documentation at Migrate API and I think there is sufficient information there for someone to write migrations. In particular, https://www.drupal.org/docs/8/api/migrate-api/migrate-destination-plugins-examples, has thorough examples. Although the title does refer to destination plugins the examples include the complete migration.yml. I expect anyone looking for how to write a migration is very likely to look at that page because it contain examples.

And of course, since they are plugins, any other properties should be documented in the Plugin Definitions

Therefor I think it is safe to mark this fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.