Remove the Skylark data configuration accessor and the only repository

use of that accessor. Data configuration access here complicates
the first phase of dynamic configuration support. And the current
use doesn't specifically need this configuration.

We can always add support back in if there's demand.

--
MOS_MIGRATED_REVID=99938987

1 files changed, 0 insertions, 8 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
index 6864e4483b..43b42ca9df 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
@@ -35,7 +35,6 @@ import com.google.devtools.build.lib.analysis.TransitiveInfoCollection;
 import com.google.devtools.build.lib.analysis.config.BuildConfiguration;
 import com.google.devtools.build.lib.collect.nestedset.NestedSet;
 import com.google.devtools.build.lib.packages.Attribute;
-import com.google.devtools.build.lib.packages.Attribute.ConfigurationTransition;
 import com.google.devtools.build.lib.packages.ImplicitOutputsFunction;
 import com.google.devtools.build.lib.packages.ImplicitOutputsFunction.SkylarkImplicitOutputsFunction;
 import com.google.devtools.build.lib.packages.OutputFile;
@@ -333,13 +332,6 @@ public final class SkylarkRuleContext {
     return ruleContext.getHostConfiguration();
   }
 
-  @SkylarkCallable(name = "data_configuration", structField = true,
-      doc = "Returns the data configuration. See the <a href=\"#modules.configuration\">"
-          + "configuration</a> type for more details.")
-  public BuildConfiguration getDataConfiguration() {
-    return ruleContext.getConfiguration().getConfiguration(ConfigurationTransition.DATA);
-  }
-
   @SkylarkCallable(structField = true,
       doc = "A <code>struct</code> containing all the output files."
           + " The struct is generated the following way:<br>"